Signaling to support mobile integrated access and backhaul

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a wireless communication device may receive mobility state information associated with an integrated access backhaul (IAB) node. The mobility state information may include information associated with at least one of: a level of mobility of the IAB node, or a change in mobility of the IAB node. The wireless communication device may perform an operation based at least in part on the mobility state information associated with the IAB node. In some aspects, a wireless communication device may determine that mobility state information associated with an IAB node is to be transmitted, and may transmit the mobility state information associated with the IAB node based at least in part on the determination. Numerous other aspects are provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/947,496, filed Aug. 4, 2020, entitled “SIGNALING TO SUPPORT MOBILEINTEGRATED ACCESS AND BACKHAUL,” which claims priority to U.S.Provisional Patent Application No. 62/884,584, filed on Aug. 8, 2019,entitled “SIGNALING TO SUPPORT MOBILE INTEGRATED ACCESS AND BACKHAUL,”the contents of which are incorporated herein by reference in theirentireties.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication, and more specifically, to techniques and apparatuses forsignaling to support mobility in an integrated access and backhaul (IAB)network.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (for example,bandwidth, transmit power, or a combination thereof). Examples of suchmultiple-access technologies include code division multiple access(CDMA) systems, time division multiple access (TDMA) systems,frequency-division multiple access (FDMA) systems, orthogonalfrequency-division multiple access (OFDMA) systems, single-carrierfrequency-division multiple access (SC-FDMA) systems, time divisionsynchronous code division multiple access (TD-SCDMA) systems, and LongTerm Evolution (LTE). LTE/LTE-Advanced is a set of enhancements to theUniversal Mobile Telecommunications System (UMTS) mobile standardpromulgated by the Third Generation Partnership Project (3GPP).

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent user equipments (UEs) to communicate on a municipal, national,regional, and even global level. New Radio (NR), which may also bereferred to as 5G, is a set of enhancements to the LTE mobile standardpromulgated by the 3GPP. NR is designed to better support mobilebroadband Internet access by improving spectral efficiency, loweringcosts, improving services, making use of new spectrum, and betterintegrating with other open standards using orthogonal frequencydivision multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on thedownlink (DL), using CP-OFDM or SC-FDM (for example, also known asdiscrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL),as well as supporting beamforming, multiple-input multiple-output (MIMO)antenna technology, and carrier aggregation. However, as the demand formobile broadband access continues to increase, there exists a need forfurther improvements in LTE and NR technologies. Preferably, theseimprovements are applicable to other multiple access technologies andthe telecommunication standards that employ these technologies.

A radio access network may include a wireless backhaul network,sometimes referred to as an integrated access and backhaul (IAB)network. In an IAB network, at least one base station acts as an anchorbase station (also referred to as an IAB donor) that communicates with acore network (via a wired backhaul link). The IAB network may includeone or more non-anchor base stations (also referred to as IAB nodes),that may communicate directly with or indirectly with (for example, viaone or more other non-anchor base stations) the anchor base station viaone or more wireless backhaul links to form a backhaul path to the corenetwork. In a typical IAB network, IAB nodes (for example, non-anchorbase stations) are stationary (that is, non-moving). Conversely, in amobile IAB network, some of the IAB nodes may be moved or capable ofmotion throughout some or all of the IAB network. For example, such IABnodes (referred to herein as “mobile IAB nodes”) may be characterized asbeing in, or being capable of being in, a state of motion (referred toherein as a “mobility state”). For example, a mobile IAB node may beinstalled on a vehicle (for example, a bus, a train, a taxi). In amobile IAB network, there may be a mix of stationary and mobile IABnodes. A mobility state of a given IAB node can impact operation of themobile IAB network. For example, the performance of a number of IABnetwork-related operations may depend on the mobility states of mobileIAB nodes. Such IAB network-related operations may include, for example,IAB topology and resource management, local scheduling, beam management,beam tracking, synchronization tracking, positioning, quality of service(QoS) type support identification, access, and paging, among otherexamples. Thus, knowledge of the mobility state of a given IAB node maybe desirable to facilitate the performance of the mobile IAB network.

SUMMARY

In some aspects, a method of wireless communication, performed by awireless communication device, may include receiving mobility stateinformation associated with an integrated access backhaul (IAB) node,wherein the mobility state information includes information associatedwith at least one of: a level of mobility of the IAB node, or a changein mobility of the IAB node; and performing an operation based at leastin part on the mobility state information associated with the IAB node.

In some aspects, a method of wireless communication, performed by awireless communication device, may include determining that mobilitystate information associated with an IAB node is to be transmitted,wherein the mobility state information includes information associatedwith at least one of: a level of mobility of the IAB node, or a changein mobility of the IAB node; and transmitting the mobility stateinformation associated with the IAB node based at least in part on thedetermination that the mobility state information is to be transmitted.

In some aspects, a wireless communication device for wirelesscommunication may include memory and one or more processors operativelycoupled to the memory. The memory and the one or more processors may beconfigured to receive mobility state information associated with an IABnode, wherein the mobility state information includes informationassociated with at least one of: a level of mobility of the IAB node, ora change in mobility of the IAB node; and perform an operation based atleast in part on the mobility state information associated with the IABnode.

In some aspects, a wireless communication device may include memory andone or more processors operatively coupled to the memory. The memory andthe one or more processors may be configured to determine that mobilitystate information associated with an IAB node is to be transmitted,wherein the mobility state information includes information associatedwith at least one of: a level of mobility of the IAB node, or a changein mobility of the IAB node; and transmit the mobility state informationassociated with the IAB node based at least in part on the determinationthat the mobility state information is to be transmitted.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a wirelesscommunication device, may cause the one or more processors to: receivemobility state information associated with an IAB node, wherein themobility state information includes information associated with at leastone of: a level of mobility of the IAB node, or a change in mobility ofthe IAB node; and perform an operation based at least in part on themobility state information associated with the IAB node.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a wirelesscommunication device, may cause the one or more processors to: determinethat mobility state information associated with an IAB node is to betransmitted, wherein the mobility state information includes informationassociated with at least one of: a level of mobility of the IAB node, ora change in mobility of the IAB node; and transmit the mobility stateinformation associated with the IAB node based at least in part on thedetermination that the mobility state information is to be transmitted.

In some aspects, an apparatus for wireless communication may includemeans for receiving mobility state information associated with an IABnode, wherein the mobility state information includes informationassociated with at least one of: a level of mobility of the IAB node, ora change in mobility of the IAB node; and means for performing anoperation based at least in part on the mobility state informationassociated with the IAB node.

In some aspects, an apparatus for wireless communication may includemeans for determining that mobility state information associated with anIAB node is to be transmitted, wherein the mobility state informationincludes information associated with at least one of: a level ofmobility of the IAB node, or a change in mobility of the IAB node; andmeans for transmitting the mobility state information associated withthe IAB node based at least in part on the determination that themobility state information is to be transmitted.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, or processing system assubstantially described with reference to and as illustrated by thedrawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples in accordance with the disclosure in order thatthe detailed description that follows may be better understood.Additional features and advantages will be described hereinafter. Theconception and specific examples disclosed may be readily utilized as abasis for modifying or designing other structures for carrying out thesame purposes of the present disclosure. Such equivalent constructionsdo not depart from the scope of the appended claims. Characteristics ofthe concepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purposesof illustration and description, and not as a definition of the limitsof the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only some typical aspects of this disclosure and aretherefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a block diagram illustrating an example wireless network inaccordance with various aspects of the present disclosure.

FIG. 2 is a block diagram illustrating an example base station (BS) incommunication with a user equipment (UE) in a wireless network inaccordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating examples of radio access networks, inaccordance with various aspects of the present disclosure.

FIG. 4 is a diagram illustrating an example of an integrated access andbackhaul (IAB) network architecture in accordance with various aspectsof the disclosure.

FIG. 5 is a diagram illustrating an example of signaling for support ofmobile IAB networking in accordance with various aspects of the presentdisclosure.

FIG. 6 is a diagram illustrating an example process performed by awireless communication device that supports mobile IAB in accordancewith various aspects of the present disclosure.

FIG. 7 is a diagram illustrating an example process performed by awireless communication device that supports mobile IAB in accordancewith various aspects of the present disclosure.

FIGS. 8 and 9 are block diagrams of example apparatuses for wirelesscommunication in accordance with various aspects of the presentdisclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and are not to be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. Based on theteachings herein one skilled in the art may appreciate that the scope ofthe disclosure is intended to cover any aspect of the disclosuredisclosed herein, whether implemented independently of or combined withany other aspect of the disclosure. For example, an apparatus may beimplemented or a method may be practiced using any quantity of theaspects set forth herein. In addition, the scope of the disclosure isintended to cover such an apparatus or method which is practiced usingother structure, functionality, or structure and functionality inaddition to or other than the various aspects of the disclosure setforth herein. Any aspect of the disclosure disclosed herein may beembodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, or combinationsthereof (collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

It should be noted that while aspects may be described herein usingterminology commonly associated with 3G or 4G wireless technologies,aspects of the present disclosure can be applied in othergeneration-based communication systems, such as 5G and later, includingNR technologies.

In a typical IAB network, IAB nodes (for example, non-anchor basestations) are stationary (that is, non-moving). Conversely, in a mobileIAB network, some of the IAB nodes may be moved or capable of motionthroughout some or all of the IAB network. For example, such IAB nodes(referred to herein as “mobile IAB nodes”) may be characterized as beingin, or being capable of being in, a state of motion (referred to hereinas a “mobility state”). For example, an IAB node may be installed on avehicle (for example, a bus, a train, a taxi) for providing networkaccess to passengers in the vehicle. In a mobile IAB network, there maybe a mix of stationary and mobile IAB nodes.

Information associated with a mobility state of an IAB node (hereinreferred to as mobility state information) may include, for example,information describing a level of mobility (for example, stationary,low-speed mobility, medium-speed mobility, high-speed mobility). Asanother example, the mobility state information may include informationdescribing a change or a transition from one level of mobility toanother (for example, the level of mobility of an IAB node may change ortransition over time). For example, a mobile IAB node may transition tostationary (for example, from low-speed mobility), or may transitionfrom one mobility class to another (for example, from medium-speedmobility to high-speed mobility).

The mobility state of a given IAB node can impact operation of themobile IAB network. For example, the performance of a number of IABnetwork-related operations may depend on the mobility state of a mobileIAB node. Such IAB network-related operations may include, for example,IAB topology and resource management, local scheduling, beam management,beam tracking, synchronization tracking, positioning, QoS type support,access, and paging, among other examples. Thus, knowledge of themobility state of a given IAB node may be desirable to facilitateefficient operation and acceptable performance of the mobile IABnetwork.

Some aspects described herein provide techniques and apparatuses forsignaling to support mobility in an IAB network (also referred to hereinas supporting “mobile IAB”). In some aspects, as described below,mobility state information (for example, including informationassociated with a level of mobility or a change of mobility of a givenIAB node), may be received, transmitted, or requested by various nodesin the mobile IAB network (for example, an IAB donor, a non-donor IABnode, or a UE). For example, a wireless communication device, such as anIAB donor or an IAB node, may receive mobility state informationassociated with another IAB node, and perform an operation based atleast in part on the mobility state information. The operation caninclude, for example, transmitting or relaying the mobility stateinformation to another device in the IAB network, or can include an IABnetwork-related operation, such as an operation associated with IABtopology and resource management, local scheduling, beam management,beam tracking, synchronization tracking, positioning, QoS type support,access, or paging. In some aspects, signaling over different interfacesand at different protocol stack layers may be defined in order tosupport the transmission and reception of mobility state information, asdescribed below.

Particular aspects of the subject matter described in this disclosurecan be implemented to realize one or more of the following potentialadvantages. In some aspects, the described signaling to support mobileIAB enables the mobility state or other characteristic of the motion ofa given IAB node to be taken into account by the IAB network. Taking theIAB node mobility into account can improve performance of an IABnetwork-related operation that may be impacted by the mobility of agiven IAB node. Thus, signaling to support mobile IAB can improveoverall performance of the IAB network and increase efficiency of theIAB network (in terms of, for example, resource utilization).

FIG. 1 is a block diagram illustrating an example wireless network inaccordance with various aspects of the present disclosure. The wirelessnetwork may be a Long Term Evolution (LTE) network or some otherwireless network, such as a 5G or NR network. The wireless network mayinclude a quantity of base stations (BSs) 110 (shown as BS 110 a, BS 110b, BS 110 c, and BS 110 d) and other network entities. A BS is an entitythat communicates with user equipment (UE(s)) and may also be referredto as a Node B, an eNodeB, an eNB, a gNB, a NR BS, a 5G node B (NB), anaccess point (AP), a transmit receive point (TRP), or combinationsthereof (these terms are used interchangeably herein). Each BS mayprovide communication coverage for a particular geographic area. In3GPP, the term “cell” can refer to a coverage area of a BS or a BSsubsystem serving this coverage area, depending on the context in whichthe term is used.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, or another type of cell. A macro cell may cover a relativelylarge geographic area (for example, several kilometers in radius) andmay allow unrestricted access by UEs with service subscription. A picocell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (for example, a home) and mayallow restricted access by UEs having association with the femto cell(for example, UEs in a closed subscriber group (CSG)). ABS for a macrocell may be referred to as a macro BS. A BS for a pico cell may bereferred to as a pico BS. ABS for a femto cell may be referred to as afemto BS or a home BS. ABS may support one or multiple (for example,three) cells.

The wireless network may be a heterogeneous network that includes BSs ofdifferent types, for example, macro BSs, pico BSs, femto BSs, relay BSs,or combinations thereof. These different types of BSs may have differenttransmit power levels, different coverage areas, and different impactson interference in the wireless network. For example, macro BSs may havea high transmit power level (for example, 5 to 40 watts) whereas picoBSs, femto BSs, and relay BSs may have lower transmit power levels (forexample, 0.1 to 2 watts). In the example shown in FIG. 1 , a BS 110 amay be a macro BS for a macro cell 102 a, a BS 110 b may be a pico BSfor a pico cell 102 b, and a BS 110 c may be a femto BS for a femto cell102 c. A network controller 130 may couple to the set of BSs 102 a, 102b, 110 a and 110 b, and may provide coordination and control for theseBSs. Network controller 130 may communicate with the BSs via a backhaul.The BSs may also communicate with one another, for example, directly orindirectly via a wireless or wireline backhaul.

In some aspects, a cell may not be stationary, rather, the geographicarea of the cell may move in accordance with the location of a mobileBS. In some aspects, the BSs may be interconnected to one another or toone or more other BSs or network nodes (not shown) in the wirelessnetwork through various types of backhaul interfaces such as a directphysical connection, a virtual network, or combinations thereof usingany suitable transport network.

The wireless network may also include relay stations. A relay station isan entity that can receive a transmission of data from an upstreamstation (for example, a BS or a UE) and send a transmission of the datato a downstream station (for example, a UE or a BS). A relay station mayalso be a UE that can relay transmissions for other UEs. In the exampleshown in FIG. 1 , a relay station 110 d may communicate with macro BS110 a and a UE 120 d in order to facilitate communication between BS 110a and UE 120 d. A relay station may also be referred to as a relay BS, arelay base station, a relay, or combinations thereof.

UEs 120 (for example, 120 a, 120 b, 120 c) may be dispersed throughoutthe wireless network, and each UE may be stationary or mobile. A UE mayalso be referred to as an access terminal, a terminal, a mobile station,a subscriber unit, a station, or combinations thereof. A UE may be acellular phone (for example, a smart phone), a personal digitalassistant (PDA), a wireless modem, a wireless communication device, ahandheld device, a laptop computer, a cordless phone, a wireless localloop (WLL) station, a tablet, a camera, a gaming device, a netbook, asmartbook, an ultrabook, a medical device or equipment, biometricsensors/devices, wearable devices (smart watches, smart clothing, smartglasses, smart wrist bands, smart jewelry (for example, smart ring,smart bracelet)), an entertainment device (for example, a music or videodevice, or a satellite radio), a vehicular component or sensor, smartmeters/sensors, industrial manufacturing equipment, a global positioningsystem device, or any other suitable device that is configured tocommunicate via a wireless medium.

Some UEs may be considered machine-type communication (MTC) or evolvedor enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEsinclude, for example, robots, drones, remote devices, sensors, meters,monitors, location tags, or combinations thereof, that may communicatewith a base station, another device (for example, remote device), orsome other entity. A wireless node may provide, for example,connectivity for or to a network (for example, a wide area network suchas Internet or a cellular network) via a wired or wireless communicationlink. Some UEs may be considered Internet-of-Things (IoT) devices, ormay be implemented as NB-IoT (narrowband internet of things) devices.Some UEs may be considered a Customer Premises Equipment (CPE). UE 120may be included inside a housing that houses components of UE 120, suchas processor components, memory components, or combinations thereof.

In general, any quantity of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies orfrequency channels. A frequency may also be referred to as a carrier, orcombinations thereof. Each frequency may support a single radio accesstechnology (RAT) in a given geographic area in order to avoidinterference between wireless networks of different RATs. In some cases,NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (for example, shown as UE 120 a andUE 120 e) may communicate directly with one another using one or moresidelink channels (for example, without using a base station 110 as anintermediary). For example, the UEs 120 may communicate usingpeer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (for example,which may include a vehicle-to-vehicle (V2V) protocol, avehicle-to-infrastructure (V2I) protocol, or combinations thereof), amesh network, or combinations thereof. In this case, the UE 120 mayperform scheduling operations, resource selection operations, or otheroperations described elsewhere herein as being performed by the basestation 110.

FIG. 2 is a block diagram illustrating an example base station (BS) incommunication with a user equipment (UE) in a wireless network inaccordance with various aspects of the present disclosure. Base station110 may be equipped with T antennas 234 a through 234 t, and UE 120 maybe equipped with R antennas 252 a through 252 r, where in general T≥1and R≥1.

At base station 110, a transmit processor 220 may receive data from adata source 212 for one or more UEs, select one or more modulation andcoding schemes (MCSs) for each UE based at least in part on channelquality indicators (CQIs) received from the UE, process (for example,encode) the data for each UE based at least in part on the MCS(s)selected for the UE, and provide data symbols for all UEs. Transmitprocessor 220 may also process system information (for example, forsemi-static resource partitioning information (SRPI), or combinationsthereof) and control information (for example, CQI requests, grants,upper layer signaling, or combinations thereof) and provide overheadsymbols and control symbols. Transmit processor 220 may also generatereference symbols for reference signals (for example, the cell-specificreference signal (CRS)) and synchronization signals (for example, theprimary synchronization signal (PSS) and secondary synchronizationsignal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO)processor 230 may perform spatial processing (for example, precoding) onthe data symbols, the control symbols, the overhead symbols, or thereference symbols, if applicable, and may provide T output symbolstreams to T modulators (MODs) 232 a through 232 t. Each MOD 232 mayprocess a respective output symbol stream (for example, for OFDM, orcombinations thereof) to obtain an output sample stream. Each MOD 232may further process (for example, convert to analog, amplify, filter,and upconvert) the output sample stream to obtain a downlink signal. Tdownlink signals from MODs 232 a through 232 t may be transmitted via Tantennas 234 a through 234 t, respectively. In accordance with variousaspects described in more detail below, the synchronization signals canbe generated with location encoding to convey additional information.

At UE 120, antennas 252 a through 252 r may receive the downlink signalsfrom base station 110 or other base stations and may provide receivedsignals to R demodulators (DEMODs) 254 a through 254 r, respectively.Each DEMOD 254 may condition (for example, filter, amplify, downconvert,and digitize) a received signal to obtain input samples. Each DEMOD 254may further process the input samples (for example, for OFDM, orcombinations thereof) to obtain received symbols. A MIMO detector 256may obtain received symbols from all R DEMODs 254 a through 254 r,perform MIMO detection on the received symbols if applicable, andprovide detected symbols. A receive processor 258 may process (forexample, decode) the detected symbols, provide decoded data for UE 120to a data sink 260, and provide decoded control information and systeminformation to a controller/processor 280. A channel processor maydetermine a reference signal received power (RSRP), a received signalstrength indicator (RSSI), a reference signal received quality (RSRQ), achannel quality indicator (CQI), or combinations thereof. In someaspects, one or more components of UE 120 may be included in a housing.

On the uplink, at UE 120, a transmit processor 264 may receive andprocess data from a data source 262 as well as control information (forexample, for reports including RSRP, RSSI, RSRQ, CQI, or combinationsthereof) from controller/processor 280. Transmit processor 264 may alsogenerate reference symbols for one or more reference signals. Thesymbols from transmit processor 264 may be precoded by a TX MIMOprocessor 266 if applicable, further processed by MODs 254 a through 254r (for example, for discrete Fourier transform spread orthogonalfrequency division multiplexing (DFT-s-OFDM), orthogonal frequencydivision multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM), orcombinations thereof), and transmitted to base station 110. At basestation 110, the uplink signals from UE 120 and other UEs may bereceived by antennas 234, processed by DEMODs 232, detected by a MIMOdetector 236 if applicable, and further processed by a receive processor238 to obtain decoded data and control information sent by UE 120.Receive processor 238 may provide the decoded data to a data sink 239and the decoded control information to controller/processor 240. Basestation 110 may include communication unit 244 and communicate tonetwork controller 130 via communication unit 244. Network controller130 may include communication unit 294, controller/processor 290, andmemory 292.

Controller/processor 240 of base station 110, controller/processor 280of UE 120, or any other component(s) of FIG. 2 may perform one or moretechniques associated with signaling to support mobile integrated accessand backhaul (IAB), as described in more detail elsewhere herein. Forexample, controller/processor 240 of base station 110,controller/processor 280 of UE 120, or any other component(s) of FIG. 2may perform or direct operations of, for example, the process of FIG. 6, the process of FIG. 7 , or other processes as described herein.Memories 242 and 282 may store data and program codes for base station110 and UE 120, respectively. A scheduler 246 may schedule UEs for datatransmission on the downlink or uplink.

In some aspects, a wireless communication device (for example, basestation 110) may include means for receiving mobility state informationassociated with an IAB node, wherein the mobility state informationincludes information associated with at least one of: a level ofmobility of the IAB node, or a change in mobility of the IAB node; meansfor performing an operation based at least in part on the mobility stateinformation associated with the IAB node; or combinations thereof. Insome aspects, such means may include one or more components of basestation 110 described in connection with FIG. 2 .

In some aspects, a wireless communication device (for example, basestation 110) may include means for determining that mobility stateinformation associated with an IAB node is to be transmitted, whereinthe mobility state information includes information associated with atleast one of: a level of mobility of the IAB node, or a change inmobility of the IAB node; means for transmitting the mobility stateinformation associated with the IAB node based at least in part on thedetermination that the mobility state information is to be transmitted;or combinations thereof. In some aspects, such means may include one ormore components of base station 110 described in connection with FIG. 2.

FIG. 3 is a diagram illustrating examples of radio access networks, inaccordance with various aspects of the disclosure. As shown by referencenumber 305, a traditional (for example, 3G, 4G, LTE, 5G, NR) radioaccess network may include multiple base stations 310 (for example,access nodes (AN)), where each base station 310 communicates with a corenetwork via a wired backhaul link 315, such as a fiber connection. Abase station 310 may communicate with a UE 320 via a wireless accesslink 325. In some aspects, a base station 310 shown in FIG. 3 maycorrespond to a base station 110 shown in FIG. 1 . Similarly, a UE 320shown in FIG. 3 may correspond to a UE 120 shown in FIG. 1 .

As shown by reference number 330, a radio access network may include awireless backhaul network, sometimes referred to as an integrated accessand backhaul (IAB) network. In an IAB network, at least one base stationis an anchor base station 335 that communicates with a core network viaa wired backhaul link 340, such as a fiber connection. An anchor basestation 335 may also be referred to as an IAB donor. The IAB network mayinclude one or more non-anchor base stations 345, sometimes referred toas relay base stations or simply as IAB nodes. The non-anchor basestation 345 may communicate directly or indirectly (for example, via oneor more other non-anchor base stations 345) with the anchor base station335 via one or more wireless backhaul links 350 to form a backhaul pathto the core network for carrying backhaul traffic. That is, in someaspects, an IAB network may be a multi-hop network, also referred toherein as a multi-hop wireless backhaul. In some aspects, each node ofan IAB network may use the same radio access technology (for example,5G/NR). Anchor base station(s) 335 or non-anchor base station(s) 345 maycommunicate with one or more UEs 355 via wireless access links 360carrying access traffic. In some aspects, nodes of the IAB network mayshare resources for access links and backhaul links, such as timeresources, frequency resources, or spatial resources. In some aspects,an anchor base station 335 or a non-anchor base station 345 shown inFIG. 3 may correspond to a base station 110 shown in FIG. 1 . Similarly,a UE 355 shown in FIG. 3 may correspond to a UE 120 shown in FIG. 1 .

As shown by reference number 365, in some aspects, a radio accessnetwork that includes an IAB network may utilize millimeter wavetechnology or directional communications (for example, beamforming,precoding) for communications between base stations or UEs (for example,between two base stations, between two UEs, or between a base stationand a UE). For example, wireless backhaul links 370 between basestations may use millimeter waves to carry information that may bedirected toward a target base station using precoding or beamforming.Similarly, the wireless access links 375 between a UE and a base stationmay use millimeter waves that may be directed toward a target wirelessnode (for example, a UE or a base station). Using beamforming fordirectional transmission may reduce inter-link interference.

In some aspects, an IAB donor includes a central unit (CU) thatconfigures IAB nodes that access a core network via the IAB donor, and adistributed unit (DU) that schedules and communicates with child nodesof the IAB donor. In some aspects, an IAB node includes a mobiletermination component (MT) that is scheduled by and that communicateswith a DU of a parent node, and a DU that schedules and communicateswith child nodes of the IAB node. A DU of an IAB node may performfunctions described in connection with a base station for that IAB node,and an MT of an IAB node may perform functions described in connectionwith a UE for that IAB node.

FIG. 4 is a diagram illustrating an example of an IAB networkarchitecture, in accordance with various aspects of the disclosure. Asshown in FIG. 4 , an IAB network may include an IAB donor 405 thatconnects to a core network via a wired connection (for example, as awireline fiber). For example, an Ng interface of an IAB donor 405 mayterminate at a core network. Additionally, or alternatively, an IABdonor 405 may connect to one or more devices of the core network thatprovide a core access and mobility management function (AMF). In someaspects, an IAB donor 405 may include a base station 110, such as ananchor base station, as described above in connection with FIG. 3 . Asshown, an IAB donor 405 may include a CU, which may perform ANCfunctions or AMF functions. The CU may configure a DU of the IAB donor405 or may configure one or more IAB nodes 410 (for example, an MT or aDU of an IAB node 410) that connect to the core network via the IABdonor 405. Thus, a CU of an IAB donor 405 may control or configure theentire IAB network that connects to the core network via the IAB donor405, such as by using control messages or configuration messages (forexample, a radio resource control (RRC) configuration message or an F1application protocol (F1AP) message).

As described above, the IAB network may include non-donor IAB nodes 410(shown as IAB nodes 1 through 4) that connect to the core network viathe IAB donor 405. As shown, an IAB node 410 may include an MT and a DU.The MT of an IAB node 410 (for example, a child node) may be controlledor scheduled by another IAB node 410 (for example, a parent node) or byan IAB donor 405. The DU of an IAB node 410 (for example, a parent node)may control or schedule other IAB nodes 410 (for example, child nodes ofthe parent node) or UEs 120. Thus, a DU may be referred to as ascheduling node or a scheduling component, and an MT may be referred toas a scheduled node or a scheduled component. In some aspects, an IABdonor 405 may include a DU and not an MT. That is, the CU of an IABdonor 405 may configure, control, or schedule communications of all IABnodes 410 or UEs 120. As another example, a UE 120 may include only anMT and not a DU. That is, communications of a UE 120 may be entirelycontrolled or scheduled by an IAB donor 405 or an IAB node 410 (forexample, a parent node of the UE 120).

When a first node controls or schedules communications for a second node(for example, when the first node provides DU functions for the secondnode's MT), the first node may be referred to as a parent node of thesecond node, and the second node may be referred to as a child node ofthe first node. Likewise, a child node of the second node may bereferred to as a grandchild node of the first node. Thus, a DU of aparent node may control or schedule communications for child nodes ofthe parent node as well as, in some instances, grandchild nodes of theparent node. A parent node may be an IAB donor 405 or an IAB node 410that has at least one child node, while a child node may be a UE 120 oran IAB node 410 that has at least one parent node. Communications of anMT of a child node may be controlled or scheduled by a parent node ofthe child node.

As further shown in FIG. 4 , a direct link between a UE 120 and an IABdonor 405, or between a UE 120 and an IAB node 410, may be referred toas an access link 415. Each access link 415 may be a direct wirelessaccess link between the respective devices that ultimately provides theUE 120 with access to a core network via the IAB donor 405 (potentiallyvia one or more backhaul links between an IAB node 410 and the IAB donor405, as described in more detail below).

As further shown in FIG. 4 , a wireless link between an IAB donor 405and an IAB node 410, or between two IAB nodes 410, may be referred to asa backhaul link 420. Each backhaul link 420 may be a wireless backhaullink that provides an IAB node 410 with radio access to a core networkvia the IAB donor 405, and potentially via one or more otherintermediate IAB nodes 410 and associated backhaul links 420. In someaspects, a backhaul link 420 may be a primary backhaul link or asecondary backhaul link (for example, a backup backhaul link to the sameparent node or to a different parent node). In some aspects, a secondarybackhaul link may be used if a primary backhaul link fails, becomescongested, or becomes overloaded. In an IAB network, network resourcesfor wireless communications (for example, time resources, frequencyresources, spatial resources) may be shared between access links 415 andbackhaul links 420.

As described above, in a typical IAB network, IAB nodes (for example,non-anchor base stations) are stationary (that is, non-moving).Conversely, in a mobile IAB network, some of the IAB nodes may be movedor capable of motion throughout some or all of the IAB network. Forexample, such IAB nodes (referred to herein as “mobile IAB nodes”) maybe characterized as being in, or being capable of being in, a state ofmotion (referred to herein as a “mobility state”). For example, an IABnode may be installed on a vehicle (for example, a bus, a train, ataxi). In a mobile IAB network, there may be a mix of stationary andmobile IAB nodes. In some cases, the mobile IAB nodes may be constrainedto be “leaf” nodes in the mobile IAB network. For example, a mobile IABnode may be permitted to be only a last-hop IAB node, that is, an IABnode that is not permitted to have any child IAB nodes. In some othercases, a mobile IAB node also may be permitted to have another IAB nodeas a child node.

In some examples, a mobile IAB node may provide an independently movingcell site. In such a case, a moving cell site (for example, a vehicle,such as a bus, a train, or a taxi) can serve surrounding UEs (forexample, in an urban area). Depending on various factors, such as thetype of vehicle, a mobile IAB node may move relatively randomly, atrelatively low speeds (for example, urban city speeds), or over arelatively large distance. In such examples, the mobility of a given UEthat is not carried in or on the vehicle is independent of the mobilityof the IAB node (that is, the movement of the UE is not predictablebased on the movement of the mobile IAB node), but may also be atrelatively low speeds (a speed similar to the mobile IAB node).

In some other examples, a mobile IAB node may provide a jointly-movingcell site (for example, a high-speed train). In such a case, a mobileIAB node may be mounted in or on the moving cell site (for example, ontop of a high-speed train) in order to serve UEs on or in the movingcell site (for example, UEs inside the high-speed train). Here, themotion of the mobile IAB node may be predictable, at relatively highspeeds, and extend over a large distance. In this use case, UEs on or inthe moving cell site move jointly with the mobile IAB node (that is, UEmovement is predictable based on the movement of the mobile IAB node).

In some other examples, a mobile IAB node may facilitate a platoon when,for example, a loose group of UEs is generally moving together. In sucha case, a single IAB node may provide network connectivity for multiplenearby UEs. For example, a mobile IAB node mounted on a first vehicledriving on a freeway may provide network connectivity for UEs in thefirst vehicle as well as for UEs in other vehicles proximal to the firstvehicle, which may be driving on the freeway in the same direction andat a similar speed. In such cases, the mobile IAB node connects to thenetwork, while other vehicles might house respective child nodes. Here,the mobile IAB node moves with local predictability, at a relativelyconstant speed, and over a relatively large distance. Further, the UEsmove jointly with the mobile IAB node.

Information associated with a mobility state of an IAB node (hereinreferred to as mobility state information) may include, for example,information describing a level of mobility (for example, stationary,low-speed mobility, medium-speed mobility, high-speed mobility). Asanother example, the mobility state information may include informationdescribing a change or a transition from one level of mobility toanother (for example, the level of mobility of an IAB node may change ortransition over time). For example, a mobile IAB node may transition tostationary (for example, from low-speed mobility), or may transitionfrom one mobility class to another (for example, from medium-speedmobility to high-speed mobility). In some instances, there may be atimer associated with such a transition (for example, an IAB node maytransition from one state to another within an indicated window oftime).

The mobility state of a given IAB node can impact operation of themobile IAB network. For example, the performance of a number of IABnetwork-related operations may depend on the mobility state of a mobileIAB node. Such IAB network-related operations may include, for example,IAB topology and resource management, local scheduling, beam management,beam tracking, synchronization tracking, positioning, QoS type support,access, and paging, among other examples. Thus, knowledge of themobility state of a given IAB node may be desirable to facilitateefficient and acceptable performance of the mobile IAB network.

Some aspects described herein provide techniques and apparatuses forsignaling to support mobility in an IAB network (also referred to hereinas supporting “mobile IAB”). In some aspects, as described below,mobility state information (for example, including informationassociated with a level of mobility or a change of mobility of a givenIAB node), may be received, transmitted, or requested by various nodesin the mobile IAB network (for example, an IAB donor, a non-donor IABnode, or a UE). For example, a wireless communication device, such as anIAB donor or an IAB node, may receive mobility state informationassociated with another IAB node, and perform an operation based atleast in part on the mobility state information. The operation caninclude, for example, transmitting or relaying the mobility stateinformation to another device in the IAB network, or can include an IABnetwork-related operation, such as an operation associated with IABtopology and resource management, local scheduling, beam management,beam tracking, synchronization tracking, positioning, QoS type support,access, or paging. In some aspects, signaling over different interfacesand at different protocol stack layers may be defined in order tosupport the transmission and reception of mobility state information, asdescribed below.

Particular aspects of the subject matter described in this disclosurecan be implemented to realize one or more of the following potentialadvantages. In some aspects, the described signaling to support mobileIAB enables the mobility state or other characteristic of the motion ofa given IAB node to be taken into account by the IAB network. Taking theIAB node mobility into account can improve performance of an IABnetwork-related operation that may be impacted by the mobility of agiven IAB node. Thus, signaling to support mobile IAB can improveoverall performance of the IAB network and increase efficiency of theIAB network (in terms of, for example, resource utilization).

FIG. 5 is a diagram illustrating an example associated with signaling tosupport mobile IAB networking in accordance with various aspects of thepresent disclosure. In FIG. 5 , a first wireless communication device(identified as WCD1) and a second wireless communication device(identified as WCD2) are nodes in a mobile IAB network. In some aspects,the first wireless communication device may be an IAB node such as afirst base station 110, a first anchor base station 335, a firstnon-anchor base station 345, a first IAB donor 405, or a first IAB node410. Similarly, the second wireless communication device may be anotherIAB node such as a second base station 110, a second anchor base station335, a second non-anchor base station 345, a second IAB donor 405, or asecond IAB node 410.

As shown in FIG. 5 , in a first operation 505, the second wirelesscommunication device may determine that mobility state informationassociated with an IAB node (for example, an IAB node 405) is to betransmitted (for example, transmitted by the second wirelesscommunication device for reception by the first wireless communicationdevice). For example, the second wireless communication device mayreceive a request or an indication to provide, to the first wirelesscommunication device, mobility state information associated with the IABnode. In some aspects, the determination may be that mobility stateinformation associated with the second wireless communication device isto be transmitted (that is, the determination may be that the secondwireless communication device is to transmit mobility state informationassociated with itself). In this scenario, the second wirelesscommunication device is the IAB node referenced in the first operation505. In some aspects, the determination may be that mobility stateinformation associated with a third wireless communication device is tobe transmitted (that is, the determination may be that the secondwireless communication device is to transmit mobility state informationassociated with the third wireless communication device after, forexample, receiving the mobility state information from the thirdwireless communication device). In this scenario, the third wirelesscommunication device is the IAB node referenced in the first operation505. Thus, in some aspects, the IAB node with which the mobility stateinformation is associated may be the IAB node itself, a parent-node ofthe IAB node, a child node of the IAB node, or another IAB node detectedby the IAB node.

In some aspects, mobility information associated with an IAB node mayinclude information that indicates the mobility state of the IAB node.For example, the mobility state information may include informationassociated with a level or state of mobility of the IAB node, such asinformation indicating whether the IAB node is stationary, has low-speedmobility (for example, is moving at a speed that is less than or equalto a first threshold), has medium-speed mobility (for example, is movingat a speed that is greater than the first threshold but is less than orequal to a second threshold), or has high-speed mobility (for example,is moving at a speed that is greater than the second threshold). Asanother example, the mobility state information may include informationassociated with a change (that is, a transition) in mobility of the IABnode, such as information indicating a transition from one mobilitystate to another, such as from the stationary state to the low-speedstate. In some aspects, the mobility state information may includeinformation indicating a time at which the transition has taken or is totake place. As another example, the mobility state information mayinclude a measurement report associated with the IAB node, such as aradio resource measurement (RRM) measurement report. As yet anotherexample, the mobility state information may include informationindicating whether the IAB node is capable of motion or being moved (forexample, an indication of whether the IAB node is a non-mobile IABnode). As described above, the mobility state of a given IAB node canimpact operation of the mobile IAB network and, therefore, knowledge ofthe mobility state may be needed in order to facilitate efficient andacceptable performance of the mobile IAB network.

In some aspects, the determination that the mobility state informationis to be transmitted may be based at least in part on an explicitrequest for the mobility state information associated with the IAB node.For example, the first wireless communication device may request themobility state information associated with the IAB node by sending arequest to the second wireless communication device. Here, the secondwireless communication device may receive the request and may transmitthe mobility state information based at least in part on the request(for example, after determining the mobility state information orreceiving the mobility state information from the IAB node).

In some aspects, the determination that the mobility state informationthat is to be transmitted may be based at least in part on a reportingconfiguration for transmitting the mobility state information associatedwith the IAB node. For example, the first wireless communication devicemay provide, to the second wireless communication device, a reportingconfiguration for transmitting the mobility state information associatedwith the IAB node. In some aspects, the reporting configuration mayindicate periodic reporting of the mobility state information (forexample, to cause the second wireless communication device to transmitthe mobility state information automatically on a periodic basis). Insome aspects, the reporting configuration may indicate aperiodicreporting of the mobility state information (for example, to cause thesecond wireless communication device to transmit the mobility stateinformation dynamically on an aperiodic basis, for example, whenrequested by the first wireless communication device). In some aspects,the reporting configuration may indicate event-triggered reporting ofthe mobility state information (for example, to cause the secondwireless communication device to transmit the mobility state informationbased at least in part on detecting an event indicated by the reportingconfiguration). Here, the second wireless communication device mayreceive the reporting configuration and provide the mobility stateinformation based at least in part on the reporting configuration (forexample, periodically, aperiodically, or based at least in part ondetecting an event).

As further shown in FIG. 5 , in a second operation 510, the secondwireless communication device may transmit the mobility stateinformation associated with the IAB node, and the first wirelesscommunication device may receive the mobility state informationassociated with the IAB node. In some aspects, the second wirelesscommunication device may transmit, and the first wireless communicationdevice may receive, the mobility state information in an RRC message,downlink control information (DCI), a layer 1 reference signal, a mediumaccess control (MAC) control element, a master information block (MIB),a random access channel (RACH) message, a system information block(SIB), a handover request message, a secondary node (SN) additionrequest message, or another type of communication. In some aspects, whentransmitting the mobility state information, the second wirelesscommunication device may broadcast the mobility state information forreception by the first wireless communication device or one or moreother wireless communication devices (for example, one or more other IABnodes 410). In some aspects, the reporting configuration may indicate aconfiguration for broadcasting the mobility state information.

In some aspects, the second wireless communication device may transmitat least a portion of the mobility state information in a communicationthat explicitly indicates the mobility state information. Thus, in someaspects, the first wireless communication device may receive themobility state information in a communication that includes or otherwiseexplicitly indicates the mobility state information. Additionally oralternatively, in some aspects, the second wireless communication devicemay transmit at least a portion of the mobility state information in acommunication that implicitly indicates the mobility state information.For example, at least a portion of the mobility state information may beimplicitly indicated based at least in part on a set of resources overwhich a signal is transmitted. Thus, in some aspects, the first wirelesscommunication device may receive the mobility state information in acommunication that implicitly indicates the mobility state informationbased on which resources were selected for transmission of the signal.

As further shown in FIG. 5 , in a third operation 515, the firstwireless communication device may perform an operation based at least inpart on the mobility state information associated with the IAB node. Forexample, the first wireless communication device may perform anoperation associated with IAB topology and resource management, localscheduling, beam management, beam tracking, synchronization tracking,positioning, QoS type support, an access procedure, paging, or anothertype of IAB network-related operation. As another example, the firstwireless communication device may provide the mobility state informationassociated with the IAB node (that is, the operation may includeproviding the mobility state information associated with the IAB node).In some aspects, the first wireless communication device may transmitthe indication of the mobility state information to, for example, an IABdonor (for example, an IAB donor 405) for provision to the CU of the IABdonor, or to another IAB node (that is, an IAB node 410 other than thatwith which the mobility state information is associated) for provisionto a DU or an MT of the other IAB node. In one example, the firstwireless communication device may be a parent node (for example, a firstIAB node 410) and the second wireless communication device may be achild node (for example, a second IAB node 410). Here, the parent nodemay be provided with mobility state information associated with thechild IAB node. The mobility state information can be used for variouspurposes, such as resource management, local scheduling, beammanagement, beam tracking, synchronization tracking, positioning, QoStype support, paging, among other examples. For such purposes, themobility state information should be provided to a DU of the parentnode. In some examples, a DU of the child node may broadcast themobility state information for reception by the DU of the parent node.In some other examples, an MT of the child node may provide the mobilitystate information directly to the DU of the parent node (for example,over a Uu interface). In some other examples, a CU of an IAB donor (forexample, an IAB donor 405) may provide the mobility state information tothe DU of the parent node. As a particular example, an MT of the childnode may provide (for example via an RRC message) the mobility stateinformation to a CU of the IAB donor, and the CU of the IAB donor mayprovide (for example, via an F1-AP message) the mobility stateinformation to the DU of the parent node. As another particular example,the DU of the child node may provide (for example, via an F1-AP message)the mobility state information to the CU of the IAB donor, and the CU ofthe IAB donor may provide (for example, via an F1-AP message) themobility state information to the DU of the parent node.

In another example, the first wireless communication device may be achild node and the second wireless communication device may be a parentnode of the child node. Here, the child node may be provided withmobility state associated with the parent node. The mobility stateinformation can be used for various purposes, such as beam management,beam tracking, synchronization tracking, positioning, QoS type support,an access procedure, among other examples. For such purposes, themobility state information should be provided to a DU or an MT of thechild node. In some examples, a DU of the parent node may broadcast themobility state information for reception by the DU or the MT of thechild node. In some other examples, a DU of the parent node may providethe mobility state information directly to the MT of the child node (forexample, over a Uu interface). In some other examples, a CU of an IABdonor may provide the mobility state information to the child node. As aparticular example, an MT of the parent node may provide (for examplevia an RRC message) the mobility state information to a CU of the IABdonor, and the CU of the IAB donor may provide (for example, via anF1-AP message) the mobility state information to the DU of the parentnode or may provide (for example, via an RRC message) the mobility stateinformation to the MT of the child node. As another particular example,the DU of the parent node may provide (for example, via an F1-APmessage) the mobility state information to the CU of the IAB donor, andthe CU of the IAB donor may provide (for example, via an F1-AP message)the mobility state information to the DU of the parent node or mayprovide (for example, via an RRC message) the mobility state informationto the MT of the child node.

In another example, the first wireless communication device may be anIAB donor and the second wireless communication device may be an IABnode. Here, a CU of the IAB donor may be provided with the mobilitystate of the IAB node. The mobility state information can be used forvarious, such as IAB topology and resource management, beam management,synchronization, positioning, QoS type support, an access procedure,paging, or another type of IAB network-related operation. Additionallyor alternatively, the CU may to provide or relay the mobility stateinformation to a third wireless communication device (for example,another IAB node or network entity, such as another IAB node 410). Insome examples, an MT of the IAB node may provide the mobility stateinformation to the CU of the IAB donor (for example, via an RRCmessage). In some other examples, a DU of the IAB node may provide themobility state information to the CU of the IAB donor (for example, viaan F1-AP message).

As described above, in some examples, the first wireless communicationdevice may be an IAB donor (for example, an IAB donor 405) and themobility state information may be received by a CU of the IAB donor.Here, the second wireless communication device may be the IAB node (thatis, the IAB node with which the mobility state information isassociated) and a DU or an MT of the second wireless communicationdevice may transmit the mobility state information to the CU of the IABdonor. Alternatively, the second wireless communication device may beanother IAB node (that is, an IAB node 410 other than the IAB node withwhich the mobility state information is associated), and a DU or an MTof the second wireless communication device may transmit the mobilitystate information to the CU of the IAB donor. In some aspects, when themobility state information is transmitted and received by a DU and a CU,respectively, the mobility state information may be communicated via anF1-AP interface. In some aspects, when the mobility state information istransmitted and received by an MT and a CU, respectively, the mobilitystate information may be communicated via a Uu interface (for example,in an RRC message, such as in a SIB).

As another alternative, when the first wireless communication device isan IAB donor, the second wireless communication device may be anotherIAB donor (for example, another IAB donor 405). Here, a CU of the secondwireless communication device may transmit the mobility stateinformation to the CU of the first wireless communication device. Insome aspects, when the mobility state information is transmitted andreceived by a CU and a CU, respectively, the mobility state informationmay be communicated via an X2/Xn interface. In some aspects, CU-CUcommunication of the mobility state information may be used forinter-donor parent-node migration or dual connectivity (DC) via multipleIAB donors. In some such examples, the mobility state information may beincluded in a handover request message transmitted by the serving IABdonor to the target IAB donor. In some other examples, the mobilitystate information can be included in an SN addition request messageassociated with, for example, NR DC, multi-RAT (MR) DC, orevolved-universal terrestrial radio access-NR (EN) DC. Notably, in somecases, the IAB donor may reject an RRC setup message or an X2/Xnhandover request or an SN addition request with, for example, the cause“mobility state not supported.”

In some aspects, the first wireless communication device may not be anIAB donor, but may be another IAB node (for example, a first IAB node410), and the mobility state information may be received by a DU of thefirst wireless communication device. Here, the second wirelesscommunication device may be the IAB node with which the mobility stateinformation is associated, and an MT of the second wirelesscommunication device may transmit the mobility state information to theDU of the first wireless communication device. Alternatively, the secondwireless communication device may be a different IAB node than the IABnode with which the mobility state information is associated, and an MTof the second wireless communication device may transmit the mobilitystate information to the DU of the first wireless communication device.In some aspects, when the mobility state information is transmitted andreceived by an MT and a DU, respectively, the mobility state informationmay be communicated via a Uu interface (for example, in DCI, a layer 1reference signal, a MAC control element, a MIB, a SIB1, uplink controlinformation (UCI)).

FIG. 6 is a diagram illustrating an example process 600 performed, forexample, by a wireless communication device, in accordance with variousaspects of the present disclosure. The process shown in FIG. 6 is anexample where a wireless communication device (for example, base station110, anchor base station 335, non-anchor base station 345, IAB donor405, IAB node 410) performs operations associated with signaling tosupport mobile IAB.

As shown in FIG. 6 , in some aspects, the example process may includereceiving mobility state information associated with an IAB node,wherein the mobility state information includes information associatedwith at least one of a level of mobility of the IAB node, or a change inmobility of the IAB node (block 610). For example, the wirelesscommunication device (for example, using transmit processor 220, receiveprocessor 238, controller/processor 240, memory 242) may receivemobility state information associated with an IAB node (for example,non-anchor base station 345 or IAB node 410), wherein the mobility stateinformation includes information associated with at least one of a levelof mobility of the IAB node or a change in mobility of the IAB node, asdescribed above.

As further shown in FIG. 6 , in some aspects, the example process mayinclude performing an operation based at least in part on the mobilitystate information associated with the IAB node (block 620). For example,the wireless communication device (for example, using transmit processor220, receive processor 238, controller/processor 240, memory 242) mayperform an operation based at least in part on the mobility stateinformation associated with the IAB node, as described above.

The process shown in FIG. 6 may include additional aspects, such as anysingle aspect or any combination of aspects described below or inconnection with one or more other processes described elsewhere herein.

In a first additional aspect, the process 600 may further includerequesting the mobility state information associated with the IAB node,and the mobility state information is received based at least in part onrequesting the mobility state information.

In a second additional aspect, alone or in combination with the firstaspect, the process 600 may further include providing a reportingconfiguration for transmitting the mobility state information associatedwith the IAB node, and the mobility state information is received basedat least in part on the reporting configuration.

In a third additional aspect, alone or in combination with one or moreof the first and second aspects, the reporting configuration indicatesat least one of: periodic reporting of the mobility state information,aperiodic reporting of the mobility state information, orevent-triggered reporting of the mobility state information.

In a fourth additional aspect, alone or in combination with one or moreof the first through third aspects, the operation includes providing themobility state information associated with the IAB node to at least oneof: a CU of an IAB donor (for example, IAB donor 405), a DU of anotherIAB node (for example, another IAB node 410), or an MT of the other IABnode.

In a fifth additional aspect, alone or in combination with one or moreof the first through fourth aspects, the wireless communication deviceis a CU of an IAB donor (for example, IAB donor 405).

In a sixth additional aspect, alone or in combination with one or moreof the first through fifth aspects, the mobility state information isreceived from a DU of the IAB node.

In a seventh additional aspect, alone or in combination with one or moreof the first through sixth aspects, the IAB node is a first IAB node,and the mobility state information is received from a DU of a second IABnode (for example, a second IAB node 410).

In an eighth additional aspect, alone or in combination with one or moreof the first through seventh aspects, the mobility state information isreceived from an MT of the IAB node.

In a ninth additional aspect, alone or in combination with one or moreof the first through eighth aspects, the IAB node is a first IAB node,and the mobility state information is received from an MT of a secondIAB node.

In a tenth additional aspect, alone or in combination with one or moreof the first through ninth aspects, the mobility state information isreceived from a CU of another IAB donor.

In an eleventh additional aspect, alone or in combination with one ormore of the first through tenth aspects, the IAB node is a first IABnode, and the wireless communication device is a DU of a second IABnode.

In a twelfth additional aspect, alone or in combination with one or moreof the first through eleventh aspects, the mobility state information isreceived from an MT of the first IAB node.

In a thirteenth additional aspect, alone or in combination with one ormore of the first through twelfth aspects, the mobility stateinformation is received from an MT of a third IAB node.

In a fourteenth additional aspect, alone or in combination with one ormore of the first through thirteenth aspects, receiving the mobilitystate information includes receiving the mobility state information inat least one of: an RRC message, DCI, a layer 1 reference signal, a MACcontrol element, a MIB, a RACH message, a SIB, a handover requestmessage, or an SN addition request message.

In a fifteenth additional aspect, alone or in combination with one ormore of the first through fourteenth aspects, receiving the mobilitystate information includes receiving the mobility state information in acommunication that explicitly indicates the mobility state information.

In a sixteenth additional aspect, alone or in combination with one ormore of the first through fifteenth aspects, receiving the mobilitystate information includes receiving the mobility state information in acommunication that implicitly indicates the mobility state information.

In a seventeenth additional aspect, alone or in combination with one ormore of the first through sixteenth aspects, the operation is associatedwith at least one of: IAB topology and resource management, localscheduling, beam management, beam tracking, synchronization tracking,positioning, QoS type support, an access procedure, or paging.

FIG. 7 is a diagram illustrating an example process 700 performed, forexample, by a base station, in accordance with various aspects of thepresent disclosure. The process shown in FIG. 7 is an example where awireless communication device (for example, base station 110, anchorbase station 335, non-anchor base station 345, IAB donor 405, IAB node410) performs operations associated with signaling to support mobileIAB.

As shown in FIG. 7 , in some aspects, the example process may includedetermining that mobility state information associated with an IAB nodeis to be transmitted, wherein the mobility state information includesinformation associated with at least one of a level of mobility of theIAB node or a change in mobility of the IAB node (block 710). Forexample, the wireless communication device (for example, using transmitprocessor 220, receive processor 238, controller/processor 240, memory242) may determine that mobility state information associated with anIAB is to be transmitted (for example, an IAB node 410), wherein themobility state information includes information associated with at leastone of a level of mobility of the IAB node or a change in mobility ofthe IAB node, as described above.

As further shown in FIG. 7 , in some aspects, the example process mayinclude transmitting the mobility state information associated with theIAB node based at least in part on the determination that the mobilitystate information is to be transmitted (block 720). For example, thewireless communication device (for example, using transmit processor220, receive processor 238, controller/processor 240, memory 242) maytransmit the mobility state information associated with the IAB nodebased at least in part on the determination that the mobility stateinformation is to be transmitted, as described above.

The example process shown in FIG. 7 may include additional aspects, suchas any single aspect or any combination of aspects described below or inconnection with one or more other processes described elsewhere herein.

In a first additional aspect, the determination that the mobility stateinformation is to be transmitted is based at least in part on anexplicit request for the mobility state information associated with theIAB node.

In a second additional aspect, alone or in combination with the firstaspect, the process 700 may further include receiving a reportingconfiguration for transmitting the mobility state information, and themobility state information is transmitted based at least in part on thereporting configuration.

In a third additional aspect, alone or in combination with one or moreof the first and second aspects, the reporting configuration indicatesat least one of: periodic reporting of the mobility state information,aperiodic reporting of the mobility state information, orevent-triggered reporting of the mobility state information.

In a fourth additional aspect, alone or in combination with one or moreof the first through third aspects, transmitting the mobility stateinformation includes transmitting the mobility state information to a CUof an IAB donor (for example, IAB donor 405).

In a fifth additional aspect, alone or in combination with one or moreof the first through fourth aspects, the wireless communication deviceis a DU of the IAB node.

In a sixth additional aspect, alone or in combination with one or moreof the first through fifth aspects, the IAB node is a first IAB node,and the wireless communication device is a DU of a second IAB node (forexample, a second IAB node 410).

In a seventh additional aspect, alone or in combination with one or moreof the first through sixth aspects, the wireless communication device isan MT of the IAB node.

In an eighth additional aspect, alone or in combination with one or moreof the first through seventh aspects, the IAB node is a first IAB node,and the wireless communication device is an MT of a second IAB node.

In a ninth additional aspect, alone or in combination with one or moreof the first through eighth aspects, transmitting the mobility stateinformation includes transmitting the mobility state information to a CUof another IAB donor.

In a tenth additional aspect, alone or in combination with one or moreof the first through ninth aspects, the IAB node is a first IAB node,and transmitting the mobility state information includes transmittingthe mobility state information to a DU of a second IAB node.

In an eleventh additional aspect, alone or in combination with one ormore of the first through tenth aspects, the wireless communicationdevice is an MT of the first IAB node.

In a twelfth additional aspect, alone or in combination with one or moreof the first through eleventh aspects, the wireless communication deviceis an MT of a third IAB node.

In a thirteenth additional aspect, alone or in combination with one ormore of the first through twelfth aspects, transmitting the mobilitystate information includes transmitting the mobility state informationin at least one of: an RRC message, DCI, a layer 1 reference signal, aMAC control element, a MIB, a RACH message, a SIB, a handover requestmessage, or an SN addition request message.

In a fourteenth additional aspect, alone or in combination with one ormore of the first through thirteenth aspects, transmitting the mobilitystate information includes transmitting the mobility state informationin a communication that explicitly indicates the mobility stateinformation.

In a fifteenth additional aspect, alone or in combination with one ormore of the first through fourteenth aspects, transmitting the mobilitystate information includes transmitting the mobility state informationin a communication that implicitly indicates the mobility stateinformation.

Although FIG. 7 shows example blocks of process 700, in some aspects,process 700 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 7 .Additionally, or alternatively, two or more of the blocks of process 700may be performed in parallel.

FIG. 8 is a block diagram of an example apparatus 800 for wirelesscommunication in accordance with various aspects of the presentdisclosure. The apparatus 800 may be a wireless communication device, ora wireless communication device may include the apparatus 800. In someaspects, the apparatus 800 includes a reception component 802, acommunication manager 804, and a transmission component 806, which maybe in communication with one another (for example, via one or morebuses). As shown, the apparatus 800 may communicate with anotherapparatus 808 (such as a UE, a base station, or another wirelesscommunication device) using the reception component 802 and thetransmission component 806.

In some aspects, the apparatus 800 may be configured to perform one ormore operations described herein in connection with FIG. 5 .Additionally or alternatively, the apparatus 800 may be configured toperform one or more processes described herein, such as process 600 ofFIG. 6 . In some aspects, the apparatus 800 may include one or morecomponents of the wireless communication device described above inconnection with FIG. 2 .

The reception component 802 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 808. The reception component 802may provide received communications to one or more other components ofthe apparatus 800, such as the communication manager 804. In someaspects, the reception component 802 may perform signal processing onthe received communications (such as filtering, amplification,demodulation, analog-to-digital conversion, demultiplexing,deinterleaving, de-mapping, equalization, interference cancellation, ordecoding, among other examples), and may provide the processed signalsto the one or more other components. In some aspects, the receptioncomponent 802 may include one or more antennas, a demodulator, a MIMOdetector, a receive processor, a controller/processor, a memory, or acombination thereof, of the wireless communication device describedabove in connection with FIG. 2 .

The transmission component 806 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 808. In some aspects, thecommunication manager 804 may generate communications and may transmitthe generated communications to the transmission component 806 fortransmission to the apparatus 808. In some aspects, the transmissioncomponent 806 may perform signal processing on the generatedcommunications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 808. In some aspects, the transmission component 806may include one or more antennas, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the wireless communication device describedabove in connection with FIG. 2 . In some aspects, the transmissioncomponent 806 may be collocated with the reception component 802 in atransceiver.

In some aspects, the communication manager 804 may receive or may causethe reception component 802 to receive mobility state informationassociated with an IAB node. Here, the mobility state information mayinclude information associated with at least one of a level of mobilityof the IAB node or a change in mobility of the IAB node. In someaspects, the communication manager 804 may perform an operation based atleast in part on the mobility state information associated with the IABnode. In some aspects, the communication manager 804 may include acontroller/processor, a memory, a scheduler, a communication unit, or acombination thereof, of the wireless communication device describedabove in connection with FIG. 2 .

In some aspects, the communication manager 804 may request or may causethe reception component 802 to request the mobility state informationassociated with the IAB node. Here, the mobility state information maybe received based at least in part on the request.

In some aspects, the communication manager 804 may provide or may causethe transmission component 806 to provide a reporting configuration fortransmitting the mobility state information associated with the IABnode. Here, the mobility state information may be received based atleast in part on the reporting configuration.

In some aspects, the communication manager 804 may include a set ofcomponents, such as an operation component 810. Alternatively, the setof components may be separate and distinct from the communicationmanager 804. In some aspects, one or more components of the set ofcomponents may include or may be implemented within acontroller/processor, a memory, a scheduler, a communication unit, or acombination thereof, of the wireless communication device describedabove in connection with FIG. 2 . Additionally or alternatively, one ormore components of the set of components may be implemented at least inpart as software stored in a memory. For example, a component (or aportion of a component) may be implemented as instructions or codestored in a non-transitory computer-readable medium and executable by acontroller or a processor to perform the functions or operations of thecomponent.

The reception component 802 may receive mobility state informationassociated with an IAB node, the mobility state information includinginformation associated with a level of mobility of the IAB node, or achange in mobility of the IAB node.

The operation component 810 may perform an operation based at least inpart on the mobility state information associated with the IAB node.

The number and arrangement of components shown in FIG. 8 are provided asan example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 8 . Furthermore, two or more components shownin FIG. 8 may be implemented within a single component, or a singlecomponent shown in FIG. 8 may be implemented as multiple, distributedcomponents. Additionally or alternatively, a set of (one or more)components shown in FIG. 8 may perform one or more functions describedas being performed by another set of components shown in FIG. 8 .

FIG. 9 is a block diagram of an example apparatus 900 for wirelesscommunication in accordance with various aspects of the presentdisclosure. The apparatus 900 may be a wireless communication device, ora wireless communication device may include the apparatus 900. In someaspects, the apparatus 900 includes a reception component 902, acommunication manager 904, and a transmission component 906, which maybe in communication with one another (for example, via one or morebuses). As shown, the apparatus 900 may communicate with anotherapparatus 908 (such as a UE, a base station, or another wirelesscommunication device) using the reception component 902 and thetransmission component 906.

In some aspects, the apparatus 900 may be configured to perform one ormore operations described herein in connection with FIG. 5 .Additionally or alternatively, the apparatus 900 may be configured toperform one or more processes described herein, such as process 700 ofFIG. 7 . In some aspects, the apparatus 900 may include one or morecomponents of the wireless communication device described above inconnection with FIG. 2 .

The reception component 902 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 908. The reception component 902may provide received communications to one or more other components ofthe apparatus 900, such as the communication manager 904. In someaspects, the reception component 902 may perform signal processing onthe received communications (such as filtering, amplification,demodulation, analog-to-digital conversion, demultiplexing,deinterleaving, de-mapping, equalization, interference cancellation, ordecoding, among other examples), and may provide the processed signalsto the one or more other components. In some aspects, the receptioncomponent 902 may include one or more antennas, a demodulator, a MIMOdetector, a receive processor, a controller/processor, a memory, or acombination thereof, of the wireless communication device describedabove in connection with FIG. 2 .

The transmission component 906 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 908. In some aspects, thecommunication manager 904 may generate communications and may transmitthe generated communications to the transmission component 906 fortransmission to the apparatus 908. In some aspects, the transmissioncomponent 906 may perform signal processing on the generatedcommunications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 908. In some aspects, the transmission component 906may include one or more antennas, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the wireless communication device describedabove in connection with FIG. 2 . In some aspects, the transmissioncomponent 906 may be collocated with the reception component 902 in atransceiver.

In some aspects, the communication manager 904 may determine thatmobility state information associated with an IAB node is to betransmitted. Here, the mobility state information may includeinformation associated with at least one of a level of mobility of theIAB node, or a change in mobility of the IAB node. The communicationmanager 904 may transmit or may cause the transmission component 906 totransmit the mobility state information associated with the IAB nodebased at least in part on the determination that the mobility stateinformation is to be transmitted. In some aspects, the communicationmanager 904 may include a controller/processor, a memory, a scheduler, acommunication unit, or a combination thereof, of the wirelesscommunication device described above in connection with FIG. 2 .

In some aspects, the determination that the mobility state informationis to be transmitted is based at least in part on an explicit requestfor the mobility state information associated with the IAB node.

In some aspects, the communication manager 804 may receive or may causethe reception component 802 to receive a reporting configuration fortransmitting the mobility state information associated with the IABnode. Here, the communication manager 804 may transmit or may cause thetransmission component 806 to transmit the mobility state information isbased at least in part on the reporting configuration.

In some aspects, the communication manager 904 may include a set ofcomponents, such as a mobility state determination component 910.Alternatively, the set of components may be separate and distinct fromthe communication manager 904. In some aspects, one or more componentsof the set of components may include or may be implemented within acontroller/processor, a memory, a scheduler, a communication unit, or acombination thereof, of the wireless communication device describedabove in connection with FIG. 2 . Additionally or alternatively, one ormore components of the set of components may be implemented at least inpart as software stored in a memory. For example, a component (or aportion of a component) may be implemented as instructions or codestored in a non-transitory computer-readable medium and executable by acontroller or a processor to perform the functions or operations of thecomponent.

The mobility state determination component 910 may determine thatmobility state information associated with an IAB node is to betransmitted, the mobility state information including informationassociated with at least one of a level of mobility of the IAB node, ora change in mobility of the IAB node. In some aspects, the mobilitystate determination component 910 may determine characteristics ofmotion of the IAB node and may determine a mobility state and/ormobility state information associated with the IAB node based on thecharacteristics. The transmission component 906 may transmit themobility state information associated with the IAB node based at leastin part on the determination that the mobility state information is tobe transmitted.

The number and arrangement of components shown in FIG. 9 are provided asan example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 9 . Furthermore, two or more components shownin FIG. 9 may be implemented within a single component, or a singlecomponent shown in FIG. 9 may be implemented as multiple, distributedcomponents. Additionally or alternatively, a set of (one or more)components shown in FIG. 9 may perform one or more functions describedas being performed by another set of components shown in FIG. 9 .

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseform disclosed. Modifications and variations may be made in light of theabove disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Asused herein, a processor is implemented in hardware, firmware, or acombination of hardware and software.

Some aspects are described herein in connection with thresholds. As usedherein, satisfying a threshold may, depending on the context, refer to avalue being greater than the threshold, greater than or equal to thethreshold, less than the threshold, less than or equal to the threshold,equal to the threshold, not equal to the threshold, or combinationsthereof.

It will be apparent that systems or methods described herein may beimplemented in different forms of hardware, firmware, or a combinationof hardware and software. The actual specialized control hardware orsoftware code used to implement these systems or methods is not limitingof the aspects. Thus, the operation and behavior of the systems ormethods were described herein without reference to specific softwarecode—it being understood that software and hardware can be designed toimplement the systems or methods based, at least in part, on thedescription herein.

Even though particular combinations of features are recited in theclaims or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims or disclosed in the specification. Although each dependent claimlisted below may directly depend on only one claim, the disclosure ofvarious aspects includes each dependent claim in combination with everyother claim in the claim set. A phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination withmultiples of the same element (for example, a-a, a-a-a, a-a-b, a-a-c,a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering ofa, b, and c).

No element, act, or instruction used herein is to be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the terms “set” and “group” are intended to include oneor more items (for example, related items, unrelated items, acombination of related and unrelated items, or combinations thereof),and may be used interchangeably with “one or more.” Where only one itemis intended, the phrase “only one” or similar language is used. Also, asused herein, the terms “has,” “have,” “having,” or combinations thereofare intended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise.

What is claimed is:
 1. A first integrated access backhaul (IAB) donornode for wireless communication, comprising: one or more memories; andone or more processors, coupled to the one or more memories, configuredto: determine that mobility state information, associated with the firstIAB donor node or a second IAB node, is to be transmitted based at leastin part on at least one of a request for the mobility state information,an indication for the mobility state information, or a reportingconfiguration for transmitting the mobility state information, whereinthe mobility state information includes information indicating whetherthe first IAB donor node or the second IAB node is capable of motion orbeing moved; and transmit the mobility state information based at leastin part on determining that the mobility state information is to betransmitted.
 2. The first IAB donor node of claim 1, wherein the secondIAB node is a child node of the first IAB donor node.
 3. The first IABdonor node of claim 1, wherein the one or more processors, to determinethat the mobility state information is to be transmitted, are configuredto: detect the second IAB node based at least in part on the at leastone of the request, the indication, or the reporting configuration; anddetermine that the mobility state information, associated with thesecond IAB node, is to be transmitted based at least in part ondetecting the second IAB node.
 4. The first IAB donor node of claim 1,wherein the one or more processors, to transmit the mobility stateinformation, are configured to transmit the mobility state informationto a third IAB node different than the second IAB node.
 5. The first IABdonor node of claim 1, wherein the one or more processors, to transmitthe mobility state information, are configured to transmit the mobilitystate information via handover request message.
 6. The first IAB donornode of claim 4, wherein the one or more processors, to transmit themobility state information to the third IAB node, are configured totransmit the mobility state information to a distributed unit of thethird IAB node.
 7. The first IAB donor node of claim 4, wherein thethird JAB node is a second IAB donor node and wherein transmitting themobility state information to the third JAB node comprises transmittingthe mobility state information to a central unit of the second IAB donornode.
 8. The first IAB donor node of claim 1, wherein the one or moreprocessors, to transmit the mobility state information, are configuredto transmit the mobility state information via an X2/Xn interface. 9.The first IAB donor node of claim 1, wherein the one or more processorsare further configured to receive the reporting configuration.
 10. Thefirst IAB donor node of claim 1, wherein the one or more processors, todetermine that the mobility state information is to be transmitted, areconfigured to: detect an event, for transmitting the mobility stateinformation, indicated in the reporting configuration; and determinethat the mobility state information is to be transmitted based at leastin part on detecting the event.
 11. The first IAB donor node of claim 1,wherein the one or more processors, to transmit the mobility stateinformation, are configured to transmit the mobility state informationin a communication that explicitly indicates the mobility stateinformation.
 12. The first IAB donor node of claim 1, wherein the one ormore processors, to transmit the mobility state information, areconfigured to transmit the mobility state information in a communicationthat implicitly indicates the mobility state information via a set ofresources over which the communication is transmitted.
 13. A method ofwireless communication performed by a first integrated access backhaul(IAB) donor node, the method comprising: determining that mobility stateinformation, associated with the first IAB donor node or a second IABnode, is to be transmitted based at least in part on at least one of arequest for the mobility state information, an indication for themobility state information, or a reporting configuration fortransmitting the mobility state information, wherein the mobility stateinformation includes information indicating whether the first IAB donornode or the second IAB node is capable of motion or being moved; andtransmitting the mobility state information based at least in part ondetermining that the mobility state information is to be transmitted.14. The method of claim 13, wherein the second IAB node is a child nodeof the first IAB donor node.
 15. The method of claim 13, whereindetermining that the mobility state information is to be transmittedcomprises: detecting the second IAB node based at least in part on theat least one of the request, the indication, or the reportingconfiguration; and determining that the mobility state information,associated with the second IAB node, is to be transmitted based at leastin part on detecting the second IAB node.
 16. The method of claim 13,wherein transmitting the mobility state information comprisestransmitting the mobility state information to a third IAB nodedifferent than the second IAB node.
 17. The method of claim 13, whereintransmitting the mobility state information comprises transmitting themobility state information to via a handover message.
 18. The method ofclaim 16, wherein transmitting the mobility state information to thethird IAB node comprises transmitting the mobility state information toa distributed unit of the third IAB node.
 19. The method of claim 16,wherein the third IAB node is a second IAB donor node and whereintransmitting the mobility state information to the third IAB nodecomprises transmitting the mobility state information to a central unitof the second IAB donor node.
 20. The method of claim 13, whereintransmitting the mobility state information comprises transmitting themobility state information to via an X2/Xn interface.
 21. The method ofclaim 13, further comprising receiving the reporting configuration. 22.The method of claim 13, wherein determining that the mobility stateinformation is to be transmitted comprises: detecting an event, fortransmitting the mobility state information, indicated in the reportingconfiguration; and determining that the mobility state information is tobe transmitted based at least in part on detecting the event.
 23. Themethod of claim 13, wherein transmitting the mobility state informationcomprises transmitting the mobility state information in a communicationthat explicitly indicates the mobility state information.
 24. The methodof claim 13, wherein transmitting the mobility state informationcomprises transmitting the mobility state information in a communicationthat implicitly indicates the mobility state information via a set ofresources over which the communication is transmitted.